Skip to main content

This is a new service – your feedback will help us to improve it.

London Borough of Hillingdon

Article 4 direction area

There is a problem

  • article-4-direction column must match the reference field in the article 4 direction dataset

Changes of use from commercial, business and service uses to dwellinghouses

reference
MA8589
name
Changes of use from commercial, business and service uses to dwellinghouses
article-4-direction

undefined

Changes of use from commercial, business and service uses to dwellinghouses
permitted-development-rights
3MA
uprns
address-texts
geometry
MULTIPOLYGON (((-0.443920 51.563255,-0.443812 51.563526,-0.443658 51.563878,-0.443556 51.564199,-0.443366 51.564390,-0.444079 51.564554,-0.444653 51.564703,-0.445053 51.564829,-0.446173 51.565259,-0.446496 51.565405,-0.446823 51.565584,-0.447271 51.565777,-0.447367 51.565809,-0.447618 51.565864,-0.447915 51.565495,-0.447789 51.565455,-0.447897 51.565320,-0.447108 51.565029,-0.447212 51.564916,-0.446565 51.564680,-0.446578 51.564666,-0.446114 51.564509,-0.445892 51.564426,-0.445419 51.564203,-0.444858 51.564019,-0.444747 51.563999,-0.444158 51.563767,-0.444380 51.563392,-0.444021 51.563267,-0.443942 51.563037,-0.444034 51.563041,-0.444083 51.563021,-0.444108 51.563001,-0.444318 51.562705,-0.443684 51.562539,-0.443673 51.562555,-0.443217 51.562921,-0.443920 51.563255)),((-0.442926 51.566145,-0.443170 51.566020,-0.443261 51.565959,-0.442876 51.565863,-0.442747 51.566030,-0.442869 51.566100,-0.442926 51.566145)))
point
POINT (-0.445314 51.564492)
notes
MA
entry-date
2024-03-27
start-date
2024-03-27
end-date

How to fix this issue

Your dataset is missing the article-4-direction column.

The Article 4 direction area guidance explains how to fix the issue:

article-4-direction

The reference for the article 4 direction used in the article 4 direction dataset.

Example: A4D1

How to improve London Borough of Hillingdon’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL